Detecting application instances that are operating improperly

ABSTRACT

A method includes determining whether an application instance has properly used computing resources to process a workload request, wherein the determination is based on one or more characteristics of the workload request to be processed. The method determines whether the application instance is operating properly, based on the determining of whether the application instance has properly used computing resources based on whether the computing resources have been accessed by the application instance a sufficient number of times; and based on the determination that the application instance is not operating properly, initiates an action to prevent the application instance from improperly processing workload.

DOMESTIC PRIORITY

This application is a continuation of co-pending U.S. patent applicationSer. No. 15/377,550, filed Dec. 13, 2016, the disclosure of which isincorporated by reference herein in its entirety.

BACKGROUND

An embodiment relates in general to detecting application instances thatare operating improperly. More specifically, an embodiment relates todetecting application instances that do not properly use computingresources.

Within a computing environment, a server generally performs or providesa specific functionality on behalf of one or more clients that requestthe specific functionality to be performed. A client can correspond to acomputing program or a computing device of a user. The specificfunctionality that is performed by a server can be functionality that isprovided by a deployed/installed application. Applications can beinstalled upon or controlled by the server, for example.

SUMMARY

According to one or more embodiments, a computer implemented methodincludes assigning response codes to computing resources and determiningwhether an application instance has properly used computing resources toprocess a workload request, wherein the determination is based on one ormore characteristics of the workload request to be processed. The methoddetermines whether the application instance is operating properly, basedon the determining of whether the application instance has properly usedcomputing resources based on whether the computing resources have beenaccessed by the application instance a sufficient number of times; andbased on the determination that the application instance is notoperating properly, initiates an action to prevent the applicationinstance from improperly processing workload.

Other embodiments of the present invention implement features of theabove-described method in computer systems and computer programproducts.

BRIEF DESCRIPTION OF THE DRAWINGS

The subject matter of one or more embodiments is particularly pointedout and distinctly defined in the claims at the conclusion of thespecification. The foregoing and other features and advantages areapparent from the following detailed description taken in conjunctionwith the accompanying drawings in which:

FIG. 1 depicts servers and a workload manager, in accordance with anembodiment;

FIG. 2 depicts a flowchart of a method in accordance with one or moreembodiments;

FIG. 3 depicts a high-level block diagram of a computer system, whichcan be used to implement one or more embodiments;

FIG. 4 depicts a computer program product, in accordance with anembodiment;

FIG. 5 depicts a cloud computing environment according to an embodiment;and

FIG. 6 depicts abstraction model layers according to an embodiment.

DETAILED DESCRIPTION

One or more embodiments can include methods and computer programproducts for detecting application instances that are operatingimproperly. Various embodiments are described herein with reference tothe related drawings. Alternative embodiments can be devised withoutdeparting from the scope of this invention. References in thespecification to “one embodiment,” “an embodiment,” “an exampleembodiment,” etc., indicate that the embodiment described can include aparticular feature, structure, or characteristic, but every embodimentmay or may not include the particular feature, structure, orcharacteristic. Moreover, such phrases are not necessarily referring tothe same embodiment. Further, when a particular feature, structure, orcharacteristic is described in connection with an embodiment, it issubmitted that it is within the knowledge of one skilled in the art toaffect such feature, structure, or characteristic in connection withother embodiments whether or not explicitly described.

Additionally, although this disclosure includes a detailed descriptionof a computing device configuration, implementation of the teachingsrecited herein are not limited to a particular type or configuration ofcomputing device(s). Rather, embodiments of the present disclosure arecapable of being implemented in conjunction with any other type orconfiguration of wireless or non-wireless computing devices and/orcomputing environments, now known or later developed.

The following definitions and abbreviations are to be used for theinterpretation of the claims and the specification. As used herein, theterms “comprises,” “comprising,” “includes,” “including,” “has,”“having,” “contains” or “containing,” or any other variation thereof,are intended to cover a non-exclusive inclusion. For example, acomposition, a mixture, process, method, article, or apparatus thatcomprises a list of elements is not necessarily limited to only thoseelements but can include other elements not expressly listed or inherentto such composition, mixture, process, method, article, or apparatus.

Additionally, the term “exemplary” is used herein to mean “serving as anexample, instance or illustration.” Any embodiment or design describedherein as “exemplary” is not necessarily to be construed as preferred oradvantageous over other embodiments or designs. The terms “at least one”and “one or more” are understood to include any integer number greaterthan or equal to one, i.e. one, two, three, four, etc. The terms “aplurality” are understood to include any integer number greater than orequal to two, i.e. two, three, four, five, etc. The term “connection”can include an indirect “connection” and a direct “connection.”

For the sake of brevity, conventional techniques related to computerprocessing systems and computing models may or may not be described indetail herein. Moreover, it is understood that the various tasks andprocess steps described herein can be incorporated into a morecomprehensive procedure, process or system having additional steps orfunctionality not described in detail herein.

It is also understood in advance that although this disclosure includesa detailed description on cloud computing, implementation of theteachings recited herein are not limited to a cloud computingenvironment. Rather, one or more embodiments are capable of beingimplemented in conjunction with any other type of computing environmentnow known or later developed.

Cloud computing is a model of service delivery for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g. networks, network bandwidth, servers, processing,memory, storage, applications, virtual machines, and services) that canbe rapidly provisioned and released with minimal management effort orinteraction with a provider of the service. This cloud model can includeat least five characteristics, at least three service models, and atleast four deployment models.

Characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provisioncomputing capabilities, such as server time and network storage, asneeded automatically without requiring human interaction with theservice's provider.

Broad network access: capabilities are available over a network andaccessed through standard mechanisms that promote use by heterogeneousthin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to servemultiple consumers using a multi-tenant model, with different physicaland virtual resources dynamically assigned and reassigned according todemand. There is a sense of location independence in that the consumergenerally has no control or knowledge over the exact location of theprovided resources but can be able to specify location at a higher levelof abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elasticallyprovisioned, in some cases automatically, to quickly scale out andrapidly released to quickly scale in. To the consumer, the capabilitiesavailable for provisioning often appear to be unlimited and can bepurchased in any quantity at any time.

Measured service: cloud systems automatically control and optimizeresource use by leveraging a metering capability at some level ofabstraction appropriate to the type of service (e.g., storage,processing, bandwidth, and active user accounts). Resource usage can bemonitored, controlled, and reported providing transparency for both theprovider and consumer of the utilized service.

Service Models are as follows:

Software as a Service (SaaS): the capability provided to the consumer isto use the provider's applications running on a cloud infrastructure.The applications are accessible from various client devices through athin client interface such as a web browser (e.g., web-based e-mail).The consumer does not manage or control the underlying cloudinfrastructure including network, servers, operating systems, storage,or even individual application capabilities, with the possible exceptionof limited user-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer isto deploy onto the cloud infrastructure consumer-created or acquiredapplications created using programming languages and tools supported bythe provider. The consumer does not manage or control the underlyingcloud infrastructure including networks, servers, operating systems, orstorage, but has control over the deployed applications and possiblyapplication hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to theconsumer is to provision processing, storage, networks, and otherfundamental computing resources where the consumer is able to deploy andrun arbitrary software, which can include operating systems andapplications. The consumer does not manage or control the underlyingcloud infrastructure but has control over operating systems, storage,deployed applications, and possibly limited control of select networkingcomponents (e.g., host firewalls).

Deployment Models are as follows:

Private cloud: the cloud infrastructure is operated solely for anorganization. It can be managed by the organization or a third party andcan exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by severalorganizations and supports a specific community that has shared concerns(e.g., mission, security requirements, policy, and complianceconsiderations). It can be managed by the organizations or a third partyand can exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the generalpublic or a large industry group and is owned by an organization sellingcloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or moreclouds (private, community, or public) that remain unique entities butare bound together by standardized or proprietary technology thatenables data and application portability (e.g., cloud bursting forload-balancing between clouds).

A cloud computing environment is service oriented with a focus onstatelessness, low coupling, modularity, and semantic interoperability.At the heart of cloud computing is an infrastructure comprising anetwork of interconnected nodes.

In a high-availability computing environment, multiple instantiations(instances) of an application may be deployed across multiple servers(or across separate functional areas of a same server), in order toensure that the application's functionality is available to the clients.For example, an application can run on two separate servers (as twoseparate instances of the application). With this example, if one serverfails to operate, the remaining operating server can still perform thefunctions of the application.

The clients can transmit their workload requests to the instances of theapplication via a shared source/port. The workload requests can bewebservice requests, for example. The shared source/port can be aworkload distribution device (such as a workload manager, for example).In one example embodiment, the instances of the application may receiveincoming workload requests from a single workload manager device. In thecourse of processing an incoming workload request, an applicationinstance will typically use corresponding computing resources to processthe request. The computing resources that are used can depend on thecharacteristics of the workload request to be performed. For example, aworkload request can require one or more stored records to be retrieved,modified, and/or changed. As such, in order to process the workloadrequests, the application can generally access a database resource,access drive/memory resources, access certain files, and/or accesscertain queues, in order to complete the processing, as discussed inmore detail below. The number of accesses, the resources to be accessed,and/or the amount of resources to be accessed can be determined based onthe workload requests that are to be processed, for example.

If a particular instance of the application operates improperly, theapplication instance can begin to improperly process incoming workloadrequests. An application instance that is operating improperly may beable to improperly process requests faster than another instance that isproperly processing the requests, because processing a requestimproperly may take less time than the time required to properly processthe same request. Therefore, as a malfunctioning application instanceimproperly processes workload requests faster than aproperly-functioning application instance, the malfunctioningapplication instance will begin to accept a larger proportion of theincoming workload requests from the shared source/port, and themalfunctioning instance will continue to improperly process the incomingworkload requests. As a larger proportion of incoming workload requestsare improperly processed more quickly, and, as a significant proportionof the workload begins to fail, a computing problem that is referred toas a “storm drain” occurs.

One or more embodiments are directed to a method and apparatus that candetermine whether or not an application instance is operating properly,based upon the resource usage of the application instance, during thecourse of processing workload requests by the application instance. Oneor more embodiments can configure/define computing policies to monitorthe resource usage of an application instance, as described in moredetail below. One or more embodiments can then determine whether theapplication instance has operated properly, based upon whether theapplication instance has properly used the resources. As describedabove, as different embodiments can use a wide variety of resources,different embodiments can define a wide variety of policies to monitorthe wide variety of resources. For example, one or more embodiments candefine policies to monitor whether or not the application instance hasaccessed a database a sufficient number of times. If an applicationinstance is determined by a policy to use an improper amount ofresources, and thus the application instance is determined to operateimproperly, the policy can initiate an action as a remedy to themalfunctioning application instance. One example action is an actionthat disables the malfunctioning application instance. Another exampleaction is an action that prevents the malfunctioning applicationinstance from receiving any more incoming workload requests.

The previous approaches generally determined whether or not anapplication instance is operating properly based upon whether or notabnormal ends and/or other externals indicators are detected. Forexample, the previous approaches may determine whether a response timeof an application instance is abnormal. With the previous approaches, ifan application instance appears to process workload requests too quickly(i.e., resulting in a response time that is too short), the previousapproaches can then conclude that the application instance is likelyoperating improperly. Previous approaches would then use workloadrouting capabilities to route incoming workloads away from theapplication instance that is determined to be operating improperly.

However, the previous approaches are generally unable to detect amalfunctioning application instance, if the malfunctioning applicationinstance does not exhibit external behavior/indicators that areobservable by the previous approaches as indicating an improperprocessing.

For example, suppose a web service request is received by amalfunctioning application instance from a shared source/port. Therequest may be a JavaScript Object Notation (JSON) Hypertext TransferProtocol (HTTP) request from a shared source/port, for example. Next,suppose that a malfunctioning application instance fails to properlyprocess the workload request because the application instance cannotaccess a required resource. Although the malfunctioning applicationinstance is unable to properly process the workload request due to aninability to access the required resource, this inability to access therequired resource is not an external indicator that is detected orrecognized by the previous approaches as indicating an improperprocessing. As such, the previous approaches are unable to detect themalfunctioning application instance.

In view of the shortcomings of the previous approaches, one or moreembodiments can determine whether or not an application instance isoperating properly, based upon whether or not resources are properlyused by the application instance during the course of workloadprocessing. As described above, one or more embodiments canconfigure/define policies that monitor the amount of resources that areused. One or more embodiments can also use policies that are alreadyavailable in policy-based management systems to monitor/determine anamount of resource in use by the application instance. One or moreembodiments can configure policies to determine whether or not anapplication instance is using sufficient resources, for example.

As an example of monitoring resource usage, one or more embodiments canconfigure a policy to monitor/determine whether an application instancehas performed a sufficient number of database accesses and/or memoryaccesses. The amount and type of resource usage that should be used bythe application instance will depend on the characteristics of thereceived workload. Suppose that an application instance receives a JSONHTTP request from a source/port, such as a request to query a customerrecord. In response to the request, suppose also that the applicationinstance is configured: (1) to perform a read call to a database toretrieve the customer record, and (2) to perform an outbound webservicecall to a web server. Suppose that the outbound webservice call is awebservice call that is associated with the retrieval of the customerrecord. For example, a banker can wish to retrieve a customer record fora customer of the bank. The banker can then wish to perform a webservicecall that is associated with the retrieved customer record, such as atransmitting of a new credit-card offer to the customer of the bank.

One or more embodiments can monitor the application instance todetermine whether the application instance has properly performed thenecessary read request. For example, one embodiment can configure apolicy that determines whether the application has performed the readrequest on the database to retrieve the customer record. The embodimentcan also configure a policy to monitor the application instance todetermine whether or not the application instance has properly performedthe outbound web service call. As discussed above, monitoring of theapplication instance can be achieved by defining one or more policiesthat initiate performing of a disabling action if the applicationinstance fails to perform the necessary successful database readrequests, and/or fails to perform the outbound web service calls. Withone embodiment, the policy can be enforced by the server upon which theapplication instance is deployed. In other embodiments, the policy canbe enforced by a computer system different than the server upon whichthe application instance is deployed.

One or more embodiments can configure separate policies for monitoringeach type of resource that is to be used. For the previous examplementioned above, an embodiment may configure a first policy to monitorthe read requests, while the embodiment may configure a second policy tomonitor the outbound web service call accessing. In both the case ofmonitoring the database read requests and the case of monitoring theoutbound webservice calls, the respective policies can perform adisabling action on the application instance, if needed. The disablingaction can be an action that disables the application instance that isbeing monitored, as discussed above.

In view of the above, one or more embodiments can determine if anapplication instance has accessed a needed resource a sufficient numberof times, such as determining whether the application instance hasperformed a sufficient number of successful database requests. If theapplication instance has not accessed a resource a sufficient number oftimes, then the application instance can be determined to have notsuccessfully processed the requests.

In the event that an application instance is disabled, other applicationinstances can continue processing the workload requests. As such,embodiments can prevent the malfunctioning application instances fromprocessing additional workload requests. In the meantime, the otherapplication instances continue processing workload requests properly,and the storm drain is avoided. As embodiments can be implemented overan existing control system, one or more embodiments can use policiesthat have already been implemented by the existing control system.

As described above, embodiments can configure their policies to initiatea disabling action (to disable an application instance) when thepolicies determine that the application is using an improper amount ofresources. Other embodiments can configure their policies to reactdifferently when detecting that an application instance is using animproper amount of resources. For example, one or more embodiments canassign different response codes to different types of accessedresources, in order to distinguish some resource accesses as being moreimportant than other resource accesses. For example, referring again tothe previous example described above, where an application instanceperforms both a read request and an outbound service call, oneembodiment can determine that the outbound service call is lessimportant than the read request. Therefore, this embodiment can assigndifferent response codes to reflect that the outbound service call isless important than the read request. The response codes can define arange of importance for accessing different resources by the applicationinstance, the range being from low importance to high importance, forexample. The importance of accessing a particular resource can be userdefined. Therefore, in the event that an application instance fails toperform the outbound service call (which corresponds to improperlyaccessing a resource of low importance), one or more embodiments canconfigure the policy to not immediately disable the applicationinstance. Rather, the policy can allow the application instance tocontinue to operate for the time being until additional conditions aremet. For example, the policy can be configured to continue allowing theapplication instance to operate until the application instance fails toaccess the lower priority resource (i.e., the outbound service call) anumber of times. In other words, embodiments may allow a certain numberof accesses to fail before disabling the application instance.

FIG. 1 depicts servers (110, 120) and a workload manager 130, inaccordance with an embodiment. As described above, one or moreapplication instances can be deployed across one or more servers. In theexample of FIG. 1, first application instance 111 is deployed on firstserver 110. Second application instance 112 and third applicationinstance 113 are deployed on second server 120. As described above, theapplication instances can receive workload requests from clients viaworkload manager 130.

FIG. 2 depicts a flowchart of a method in accordance with one or moreembodiments. The method can be performed by a server, for example. Inanother embodiment, the method can be performed by a computing devicethat operates in conjunction with a server. The method includes, atblock 210, determining whether an application instance has properly usedcomputing resources to process a workload request. The determination isbased on one or more characteristics of the workload request to beprocessed. The method also includes, at block 220, determining whetherthe application instance is operating properly, based on the determiningof whether the application instance has properly used computingresources. Based on the determination that the application instance isnot operating properly, the method, at block 230, initiates an action toprevent the application instance from improperly processing workloadrequests.

FIG. 3 depicts a high-level block diagram of a computer system 300,which can be used to implement one or more embodiments. Computer system300 can correspond to, at least, an application server, a cloudprovisioning server, a server of the end user, a workload manager,and/or a computing device of the end user. Computer system 300 can beused to implement hardware components of systems capable of performingmethods described herein. Although one exemplary computer system 300 isshown, computer system 300 includes a communication path 326, whichconnects computer system 300 to additional systems (not depicted) andcan include one or more wide area networks (WANs) and/or local areanetworks (LANs) such as the Internet, intranet(s), and/or wirelesscommunication network(s). Computer system 300 and additional system arein communication via communication path 326, e.g., to communicate databetween them.

Computer system 300 includes one or more processors, such as processor302. Processor 302 is connected to a communication infrastructure 304(e.g., a communications bus, cross-over bar, or network). Computersystem 300 can include a display interface 306 that forwards graphics,textual content, and other data from communication infrastructure 304(or from a frame buffer not shown) for display on a display unit 308.Computer system 300 also includes a main memory 310, preferably randomaccess memory (RAM), and can also include a secondary memory 312.Secondary memory 312 can include, for example, a hard disk drive 314and/or a removable storage drive 316, representing, for example, afloppy disk drive, a magnetic tape drive, or an optical disc drive. Harddisk drive 314 can be in the form of a solid state drive (SSD), atraditional magnetic disk drive, or a hybrid of the two. There also canbe more than one hard disk drive 314 contained within secondary memory312. Removable storage drive 316 reads from and/or writes to a removablestorage unit 318 in a manner well known to those having ordinary skillin the art. Removable storage unit 318 represents, for example, a floppydisk, a compact disc, a magnetic tape, or an optical disc, etc. which isread by and written to by removable storage drive 316. As will beappreciated, removable storage unit 318 includes a computer-readablemedium having stored therein computer software and/or data.

In alternative embodiments, secondary memory 312 can include othersimilar means for allowing computer programs or other instructions to beloaded into the computer system. Such means can include, for example, aremovable storage unit 320 and an interface 322. Examples of such meanscan include a program package and package interface (such as that foundin video game devices), a removable memory chip (such as an EPROM,secure digital card (SD card), compact flash card (CF card), universalserial bus (USB) memory, or PROM) and associated socket, and otherremovable storage units 320 and interfaces 322 which allow software anddata to be transferred from the removable storage unit 320 to computersystem 300.

Computer system 300 can also include a communications interface 324.Communications interface 324 allows software and data to be transferredbetween the computer system and external devices. Examples ofcommunications interface 324 can include a modem, a network interface(such as an Ethernet card), a communications port, or a PC card slot andcard, a universal serial bus port (USB), and the like. Software and datatransferred via communications interface 324 are in the form of signalsthat can be, for example, electronic, electromagnetic, optical, or othersignals capable of being received by communications interface 324. Thesesignals are provided to communications interface 324 via a communicationpath (i.e., channel) 326. Communication path 326 carries signals and canbe implemented using wire or cable, fiber optics, a phone line, acellular phone link, an RF link, and/or other communications channels.

In the present description, the terms “computer program medium,”“computer usable medium,” and “computer-readable medium” are used torefer to media such as main memory 310 and secondary memory 312,removable storage drive 316, and a hard disk installed in hard diskdrive 314. Computer programs (also called computer control logic) arestored in main memory 310 and/or secondary memory 312. Computer programsalso can be received via communications interface 324. Such computerprograms, when run, enable the computer system to perform the featuresdiscussed herein. In particular, the computer programs, when run, enableprocessor 302 to perform the features of the computer system.Accordingly, such computer programs represent controllers of thecomputer system. Thus it can be seen from the forgoing detaileddescription that one or more embodiments provide technical benefits andadvantages.

FIG. 4 depicts a computer program product 400, in accordance with anembodiment. Computer program product 400 includes a computer-readablestorage medium 402 and program instructions 404.

Embodiments can be a system, a method, and/or a computer programproduct. The computer program product can include a computer-readablestorage medium (or media) having computer-readable program instructionsthereon for causing a processor to carry out aspects of one or moreembodiments.

The computer-readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer-readable storage medium can be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer-readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer-readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer-readable program instructions described herein can bedownloaded to respective computing/processing devices from acomputer-readable storage medium or to an external computer or externalstorage device via a network, for example, the Internet, a local areanetwork, a wide area network and/or a wireless network. The network caninclude copper transmission cables, optical transmission fibers,wireless transmission, routers, firewalls, switches, gateway computers,and/or edge servers. A network adapter card or network interface in eachcomputing/processing device receives computer-readable programinstructions from the network and forwards the computer-readable programinstructions for storage in a computer-readable storage medium withinthe respective computing/processing device.

Computer-readable program instructions for carrying out embodiments caninclude assembler instructions, instruction-set-architecture (ISA)instructions, machine instructions, machine dependent instructions,microcode, firmware instructions, state-setting data, or either sourcecode or object code written in any combination of one or moreprogramming languages, including an object-oriented programming languagesuch as Smalltalk, C++ or the like, and conventional proceduralprogramming languages, such as the “C” programming language or similarprogramming languages. The computer-readable program instructions canexecute entirely on the user's computer, partly on the user's computer,as a stand-alone software package, partly on the user's computer andpartly on a remote computer or entirely on the remote computer orserver. In the latter scenario, the remote computer can be connected tothe user's computer through any type of network, including a local areanetwork (LAN) or a wide area network (WAN), or the connection can bemade to an external computer (for example, through the Internet using anInternet Service Provider). In some embodiments, electronic circuitryincluding, for example, programmable logic circuitry, field-programmablegate arrays (FPGA), or programmable logic arrays (PLA) can execute thecomputer-readable program instructions by utilizing state information ofthe computer-readable program instructions to personalize the electroniccircuitry, in order to perform one or more embodiments.

Aspects of various embodiments are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to variousembodiments. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer-readable program instructions.

These computer-readable program instructions can be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer-readable program instructionscan also be stored in a computer-readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that thecomputer-readable storage medium having instructions stored thereincomprises an article of manufacture including instructions whichimplement aspects of the function/act specified in the flowchart and/orblock diagram block or blocks.

The computer-readable program instructions can also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments. In this regard, each block in the flowchart or blockdiagrams can represent a module, segment, or portion of instructions,which comprises one or more executable instructions for implementing thespecified logical function(s). In some alternative implementations, thefunctions noted in the block can occur out of the order noted in thefigures. For example, two blocks shown in succession can, in fact, beexecuted substantially concurrently, or the blocks can sometimes beexecuted in the reverse order, depending upon the functionalityinvolved. It will also be noted that each block of the block diagramsand/or flowchart illustration, and combinations of blocks in the blockdiagrams and/or flowchart illustration, can be implemented by specialpurpose hardware-based systems that perform the specified functions oracts or carry out combinations of special purpose hardware and computerinstructions.

FIG. 5 depicts a cloud computing environment according to an embodiment.Referring FIG. 5, illustrative cloud computing environment 50 isdepicted. As described above, embodiments can be implemented within acloud computing environment. A system that performs the method of FIG. 2can also be implemented within a cloud computing environment, forexample. As shown, cloud computing environment 50 comprises one or morecloud computing nodes 10 with which local computing devices used bycloud consumers, such as, for example, personal digital assistant (PDA)or cellular telephone 54A, desktop computer 54B, and/or laptop computer54C can communicate. Nodes 10 can communicate with one another. They canbe grouped (not shown) physically or virtually, in one or more networks,such as Private, Community, Public, or Hybrid clouds as describedhereinabove, or a combination thereof. This allows cloud computingenvironment 50 to offer infrastructure, platforms and/or software asservices for which a cloud consumer does not need to maintain resourceson a local computing device. It is understood that the types ofcomputing devices 54A-N shown in FIG. 5 are intended to be illustrativeonly and that computing nodes 10 and cloud computing environment 50 cancommunicate with any type of computerized device over any type ofnetwork and/or network addressable connection (e.g., using a webbrowser).

FIG. 6 depicts abstraction model layers according to an embodiment.Referring to FIG. 6, a set of functional abstraction layers provided bycloud computing environment 50 (FIG. 5) is shown. It should beunderstood in advance that the components, layers, and functions shownin FIG. 6 are intended to be illustrative only and embodiments are notlimited thereto. As depicted, the following layers and correspondingfunctions are provided.

Hardware and software layer 60 includes hardware and softwarecomponents. Examples of hardware components include: mainframes 61; RISC(Reduced Instruction Set Computer) architecture based servers 62;servers 63; blade servers 64; storage devices 65; and networks andnetworking components 66. In some embodiments, software componentsinclude network application server software 67 and database software 68.

Virtualization layer 70 provides an abstraction layer from which thefollowing examples of virtual entities can be provided: virtual servers71; virtual storage 72; virtual networks 73, including virtual privatenetworks; virtual applications and operating systems 74; and virtualclients 75.

In one example, management layer 80 can provide the functions describedbelow. Resource provisioning 81 provides dynamic procurement ofcomputing resources and other resources that are utilized to performtasks within the cloud computing environment. Metering and Pricing 82provide cost tracking as resources are utilized within the cloudcomputing environment, and billing or invoicing for consumption of theseresources. In one example, these resources can comprise applicationsoftware licenses. Security provides identity verification for cloudconsumers and tasks, as well as protection for data and other resources.User portal 83 provides access to the cloud computing environment forconsumers and system administrators. Service level management 84provides cloud computing resource allocation and management such thatrequired service levels are met. Service Level Agreement (SLA) planningand fulfillment 85 provide pre-arrangement for, and procurement of,cloud computing resources for which a future requirement is anticipatedin accordance with an SLA.

Workloads layer 90 provides examples of functionality for which thecloud computing environment can be utilized. Examples of workloads andfunctions which can be provided from this layer include: mapping andnavigation 91; software development and lifecycle management 92; virtualclassroom education delivery 93; data analytics processing 94;transaction processing 95; and determining whether application instancesare properly operating 96.

The descriptions of the various embodiments have been presented forpurposes of illustration, but are not intended to be exhaustive orlimited to the embodiments described. Many modifications and variationswill be apparent to those of ordinary skill in the art without departingfrom the scope and spirit of the invention. The terminology used hereinwas chosen to best explain the principles of the embodiment, thepractical application or technical improvement over technologies foundin the marketplace, or to enable others of ordinary skill in the art tounderstand the embodiments described herein.

What is claimed is:
 1. A computer implemented method, the methodcomprising: assigning response codes to computing resources; determiningwhether an application instance has properly used computing resources toprocess a workload request, wherein the determination is based on one ormore characteristics of the workload request to be processed;determining whether the application instance is operating properly,based on the determining of whether the application instance hasproperly used computing resources based on whether the computingresources have been accessed by the application instance a sufficientnumber of times; and based on the determination that the applicationinstance is not operating properly and on the response code for thecomputing resource that has been accessed by the application instance aninsufficient number of times being a low importance response code:checking for an other condition; continuing operation of the applicationinstance in response to the other condition not being met; andinitiating an action to prevent the application instance from improperlyprocessing workload in response to the other condition being met.
 2. Thecomputer implemented method of claim 1, wherein determining whether anapplication instance has properly used computing resources comprisesconfiguring a computing policy to determine whether the applicationinstance has properly used computing resources.
 3. The computerimplemented method of claim 1, wherein the one or more characteristicsof the workload request includes one or more policies.
 4. The computerimplemented method of claim 1, wherein the computing resources comprisedatabase resources and/or memory resources.
 5. The computer implementedmethod of claim 1, wherein initiating the action comprises initiating anaction that disables the application instance.
 6. The computerimplemented method of claim 1, wherein the application instance receivesthe workload request from a source that is shared by other applicationinstances.
 7. A computer system comprising: a memory; and a processorsystem communicatively coupled to the memory; the processor systemconfigured to perform a method comprising: assigning response codes tocomputing resources; determining whether an application instance hasproperly used computing resources to process a workload request, whereinthe determination is based on one or more characteristics of theworkload request to be processed; determining whether the applicationinstance is operating properly, based on the determining of whether theapplication instance has properly used computing resources based onwhether the computing resources have been accessed by the applicationinstance a sufficient number of times; and based on the determinationthat the application instance is not operating properly and on theresponse code for the computing resource that has been accessed by theapplication instance an insufficient number of times being a lowimportance response code: checking for an other condition; continuingoperation of the application instance in response to the other conditionnot being met; and initiating an action to prevent the applicationinstance from improperly processing workload requests in response to theother condition being met.
 8. The computer system of claim 7, whereindetermining whether an application instance has properly used computingresources comprises configuring a computing policy to determine whetherthe application instance has properly used computing resources.
 9. Thecomputer system of claim 7, wherein the one or more characteristics ofthe workload request includes one or more policies.
 10. The computersystem of claim 7, wherein the computing resources comprise databaseresources and/or memory resources.
 11. The computer system of claim 7,wherein initiating the action comprises initiating an action thatdisables the application instance.
 12. The computer system of claim 7,wherein the application instance receives the workload request from asource that is shared by other application instances.
 13. A computerprogram product comprising: a computer-readable storage medium havingprogram instructions embodied therewith, wherein the computer-readablestorage medium is not a transitory signal per se, the programinstructions readable by a processor system to cause the processorsystem to perform a method comprising: assigning response codes tocomputing resources; determining whether an application instance hasproperly used computing resources to process a workload request, whereinthe determination is based on one or more characteristics of theworkload request to be processed; determining whether the applicationinstance is operating properly, based on the determining of whether theapplication instance has properly used computing resources based onwhether the computing resources have been accessed by the applicationinstance a sufficient number of times; and based on the determinationthat the application instance is not operating properly and on theresponse code for the computing resource that has been accessed by theapplication instance an insufficient number of times being a lowimportance response code: checking for an other condition; continuingoperation of the application instance in response to the other conditionnot being met; and initiating an action to prevent the applicationinstance from improperly processing workload requests in response to theother condition being met.
 14. The computer program product of claim 13,wherein determining whether an application instance has properly usedcomputing resources comprises configuring a computing policy todetermine whether the application instance has properly used computingresources.
 15. The computer program product of claim 13, wherein the oneor more characteristics of the workload request includes one or morepolicies.
 16. The computer program product of claim 13, wherein thecomputing resources comprise database resources and/or memory resources.17. The computer program product of claim 13, wherein initiating theaction comprises initiating an action that disables the applicationinstance.
 18. The computer program product of claim 13, wherein theapplication instance receives the workload request from a source that isshared by other application instances.